Q: I have a customer who is encountering a problem using my product. Can you
suggest a way to use MacsBug to diagnose problems at a customer site?
A: Yes. Here, in a few steps, is a technique for using MacsBug to diagnose field
problems.
Take a clean copy of the latest MacsBug. (You can find the latest MacsBug on the Tool Chest developer CD in the path
:Tool Chest:Testing & Debugging:Debuggers & dcmds:MacsBug 6.5.2
or from anonymous ftp via
MacsBug download).
Create a file using ResEdit (or Resorcerer, etc.) containing a 'mxbm' resource (the 'mxbm' resource contains macro definitions).
In this 'mxbm' resource, define the macro 'everytime' as follows:
stdloginto 'Send to the programmer'
|
This way, if MacsBug is ever invoked due to a program error, you will automatically get a log of what occurred. The log, named "Send to the
programmer" will exist on the desktop.
4) Have your customer send you the log file created by the above steps.
See Also:
- See page 219 of the MacsBug Reference and Debugging Guide, Apple
Computer (Addison-Wesley) for details of the 'everytime' macro.
- For details of what '
stdloginto' does, look at the 'mxbm' resource 'log stuff'
in MacsBug's resource fork.
|
